home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
s2a150.zip
/
TIPS.S2A
< prev
Wrap
Text File
|
1992-01-23
|
9KB
|
195 lines
This file will help you out:
■ If you don't have DORINFO1.DEF or DOOR.SYS.
■ If you want the first bulletin not abortable, but abortable on the rest.
■ When you need to create a header file.
■ If you use a RAMDRIVE.
■ If you would like to see an example 2 node setup.
■ By showing you how to run the 3 programs together.
■ When you need to start from scratch/switch to a new output format.
■ If you want to find out some other neat uses for S2A.
┌─┬────────────────────────────────────────────────────────────────────────────
│Q│ How can I make Send·2·ALL run if I have no DORINFO1.DEF or DOOR.SYS?
├─┤
│A│ Find some way to create one. There are several ways:
└─┘ 1. If you have a DORINFO.DEF or DORINFO2.DEF file or something like that,
edit your config file with S2Asetup by specifying DORINFO2.DEF instead.
If that doesn't work, rename the file to DORINFO1.DEF (this means you
will have to write a little batch file that renames the file and then
calls S2A).
2. Write or use a 3rd party conversion program that creates a DORINFO1.DEF
or DOOR.SYS. If you need to write one, consult the RASTRUCT.100 docu-
ment that comes with Remote Access.
┌─┬────────────────────────────────────────────────────────────────────────────
│Q│ How can I make the first bulletin not abortable?
├─┤
│A│ Run S@ASETUP and put the characters that cause a file to be not abortable.
└─┘ At the end of your first bulletin's text, put the characters that turn
aborting back on.
┌─┬────────────────────────────────────────────────────────────────────────────
│Q│ Umm, how do I make my own header file?
├─┤
│A│ Use an ANSI editor like TheDraw and create an ANSI file that is saved with
└─┘ NO ansi cls (clearscreen) command (a sequence of characters that starts
with the escape character and then [2J). Also the ANSI `picture' should
only use the first 22 lines. Sometimes you have to go into a text editor
and remove the added `junk' on the end of the file so that it correctly
uses just the first 22 lines.
┌─┬────────────────────────────────────────────────────────────────────────────
│Q│ I am using a RAMDRIVE; how can I make sure the bulletins are saved in case
│ │ the power goes out or I have to reboot?
├─┤
│A│ Call S2A from a batch file and have your BBS call the batch file. The
└─┘ batch file will need to look something like this:
C:\BBS\DOORS\S2A C:\BBS\DOORS\CONFIG.S2A
if errorlevel 200 COPY E:\outfile.a?? c:\BBS\text
What this does is copy the output files (as specified in config.s2a) back
to your hard drive for safe keeping. I do something similar on my
system:
if errorlevel 200 PKZIP c:\BBS\TEXT\TXTFILES E:\OUTFILE.a??
This ZIPs the newly generated files into an existing ZIP file, which I can
unZIP to the ramdrive after I reboot.
┌─┬────────────────────────────────────────────────────────────────────────────
│Q│ The docs are OK, but can you give me an example 2 node setup and tell me
│ │ how I'm supposed to run all the programs?
├─┤
│A│ Sure thing. For the sake of example I will assume that you will use a
└─┘ DOOR.SYS drop file, a BBS.BAT batch file, that you want both nodes to
see the same set of bulletins and you have the following paths (substitute
your own info as it applies):
C:\BBS ─ Path to main BBS
C:\BBS\TEXT ─ Path to your BBS's text (ANSI/ASCII) files
C:\BBS\NODE1 ─ Path to node 1 of your BBS
C:\BBS\NODE2 ─ Path to node 2 of your BBS
D:\S2A ─ Path to Send·2·ALL's directory
1. Put an option in your BBS menus to call Send-2-ALL (S2A.EXE):
■ For the node 1 menu add:
Key : P (for Post bulletin)
Data: D:\S2A\S2A.EXE D:\S2A\CONFIG.1
■ For the node 2 menu add:
Key : P (for Post bulletin)
Data: D:\S2A\S2A.EXE D:\S2A\CONFIG.2
If you are like me, you may only have 1 .MNU file for all your nodes.
In that case, `Data' should read: D:\S2A\S2A.EXE D:\S2A\CONFIG.*P
2. Run S2Asetup by typing S2ASETUP CONFIG.1
3. For now, leave all defaults as is, except for pathnames. Under
FILENAMES & PATHS put the following values in the 5 fields in
this order:
Field 1: <leave field 1 alone>
2: D:\S2A\EXHEADER.ANS
3: C:\BBS\TEXT\WELCOME1.ANS
4: C:\BBS\TEXT\WELCOME1.ASC
5: C:\BBS\NODE1\DOOR.SYS
4. Go into BULLETIN PARAMETERS and change GENERATE ON EXIT to YES.
5. Copy CONFIG.1 to CONFIG.2 and change the field (...BBS Dropfile)
containing
C:\BBS\NODE1\DOOR.SYS
to this:
C:\BBS\NODE2\DOOR.SYS
6. Add the line
D:\S2A\S2AMAINT D:\S2A\CONFIG.1
to BBS.BAT
wherever the daily event is called. (Note: Even though you are using
CONFIG.1 and not CONFIG.2, the same set of bulletins will be generated
because the same filenames were specified and the ouput is the same. If
you wanted one set of files/different output for CONFIG.1 and another
set for CONFIG.2, then you will have to put a line for both. Note also
that they will use the same data [input] file: BULLETIN.S2A, unless you
specify a different one in each file).
7. Go into the D:\S2A directory and type:
S2A CONFIG.1 /L John Doe
(You can now play with the editor,
create a bulletin under the name John Doe, and save it w/ Ctrl-Z.)
8. Delete the bulletin you created by typing:
S2AMAINT CONFIG.2 1
Note that I used config.2 instead of
config.1. It doesn't matter, because the same conditions apply as in
the note above.
┌─┬────────────────────────────────────────────────────────────────────────────
│Q│ How do I start from scratch and/or generate a new set of bulletins with a
│ │ different ouput?
├─┤
│A│ Make sure that the file specified in `Filename of Bulletin data file' does
└─┘ NOT exist. This is usually BULLETIN.S2A
Next, create a bulletin header file that has some text in it about who
the bulletin is from and to, the subject, the creation, the expiration
and the bulletin # (see EXHEADER.ANS for an idea).
Next, re-edit a (or the) config file using S2Asetup, and change whatever
fields/values you wish so that they correspond to the header file.
You're all set!
┌─┬────────────────────────────────────────────────────────────────────────────
│Q│ What other cool things can I do with S2A?
├─┤
│A│ Note that the things below will work for the ANSI portion of the output.
└─┘ The ascii output will still have the 'From:', 'To:', etc. fields.
If I get enough registrations, I will release a new version which allows
the ASCII output to be configurable. Also, any and all fields will be
able to be suppressed from being displayed.
■ BBS information lister.
- Create a header file with fields such as:
'BBS Name:' instead of 'From:'
'Sysop:' instead of 'To:'
'Focus:' instead of 'Subject:'
'Info posted on: ' instead of 'Created:'
'Valid until:' instead of 'Expires:'
'BBS #' instead of 'Bulletin:'
- Set S2ASETUP to allow aliases
- Run S2A with the parameters <configfile> /L [<BBS name>]
- Edit the text which describes the BBS
■ Online games describer
- Create a header file with fields such as:
'Game:' instead of 'From:'
'Type:' instead of 'To:'
'Object:' instead of 'Subject:'
'Info posted on: ' instead of 'Created:'
'Valid until:' instead of 'Expires:'
'Game #' instead of 'Bulletin:'
- Set S2ASETUP to allow aliases
- Run S2A with the parameters <configfile> /L [<Game name>]
- Edit the text which describes the Game
■ Shareware release manager
- Create a header file with fields such as:
'Author:' instead of 'From:'
'Software:' instead of 'To:'
'Purpose:' instead of 'Subject:'
'Beta-Test Start: ' instead of 'Created:'
'To be Released:' instead of 'Expires:'
'Number' instead of 'Bulletin:'
- Set S2ASETUP to allow aliases
- Run S2A with the parameters <configfile> /L
- Create the text which describes the Game
■ Logoff comments
■ Birthdays/special events
■ Price listings/product descriptions
■ Hey! you name it...